Manage Order API

(0 reviews)

How to use the API

Here's an overview of the features included in this API, what they do and what you can use them for:

API FeatureWhat it doesWhat it's used for
Get API VersionRetrieves the full version number of the API (major, minor and patch version numbers)Viewing the API version.
Create orderCreates an orderAllows RSPs to submit an order request if confirmed as feasible via an Order Feasibility request.
Amend orderAmends an orderAllows RSPs to manage and amend an order, update order details, contact details, raise interactions or to escalate.
Cancel orderCancels an orderAllows RSPs to cancel an order.
Get order detailsGet order detailsRetrieves order details, including status, site visits, charges, and other information relevant to the order.
Get order attachmentsGet order attachmentsRetrieves an attachment previously added to an order.
Get order notificationsGet order notificationsRetrieves any notifications associated with an order.
orderCharges array

The following values are provided by the orderCharges array.

ValueDescription
categoryCategory of the charge.
productOfferNameProduct offer name (for example: Business 1, Standard CSE).
chargeTypeType of charge for the category, for example: Recurring, One Time.
unitCostUnit cost in dollars ($) for the category selected.
Data type = decimal
quantityQuantity of category selected based on unit cost.
Data type =decimal
valueTotal value in dollars ($) of the category selected.
Data type =decimal
notificationPreference

The following values are provided by the requestNotify attribute.

ValueDescription
trueReceive email notificaitons about the order.
falseDo not receive email notifications about the order.
notificationEmail

The following values are provided by the notificationEmail attribute.

ValueDescription
notificationEmailThe email address to receive order notifications.
locationDetails

The following location and equipment access information is provided by the locationDetails array.

NameDescription
siteAccessInformationProvides any specific site information in a free text field for the technician (for example: dog on site, rear building, check in at reception, specific sign in process at data centres, health and safety procedures and certificates required on site).
Note: This field is restricted to 2000 characters.
locationOfEquipmentGuidance for the technician on where the equipment is to be installed on site (for example: install ONT to the wall in the garage).
Note: This field is restricted to 2000 characters.
retainCopper

The following values are provided by the retainCopper attribute.

ValueDescription
TrueCopper is to be retained (for example: alarm monitoring or voice over copper).
FalseCopper is not to be retained.
contactDetails

The contactDetails array is used to add contact information for order contacts.

The following values are provided by the contactDetails array.

ValueDescription
contactNameName of the primary contact on site.
contactTypeProvides details of contact types and roles.
The following contact types can be added:
- Site Contact - primary contact on site and familiar with the order
- Additional Contact - used if the order requires an additional contact person
- Order Contact - administrative person for the order
- IT Contact - IT contact person for the order
- Legal Owner - the Legal Owner of the location
- Body Corporate - Body Corporate contact person for the order
- Property Manager - Property Manager contact person for the order.
preferredPhonePreferred phone number for the primary site contact.
alternatePhoneAlternate phone number for any contact you have added to the order.
emailEmail address for any contact you have added to the order.
States and substates

Orders are managed using states and substates. As the order progresses and when scoping and installation work is carried out, the order state changes.

Note: All states apply to all orders.

The following state and substate values are provided.

State valueSubstate valueDescription
AcknowledgedReceivedThe order has been received by Chorus.
AcknowledgedAcceptedThe order has been checked and is accepted for provisioning.
In ProgressConsent RequiredConsent is required before this order can be progressed.
In ProgressConsent RequestedConsent has been requested.
In ProgressConsent Not RequiredConsent is not required for this order.
In ProgressConsent GainedConsent has been given.
In ProgressConsent DeclinedThe consent request has been declined or was not obtained within the required timeframe.
In ProgressGenerate QuotationA quote is being generated for the order.
In ProgressIntent to CancelChorus has advised the intent to cancel the order and provided a reason for the cancellation.
In ProgressNetwork DesignThe network design is currently in progress.
In ProgressNetwork BuildThe network build is currently in progress.
In ProgressScoping ScheduledScoping for this order has been scheduled.
In ProgressScheduledThe order install has been scheduled.
In ProgressInvestigation RequiredIdentified as a potential multi dwelling unit (MDU) or right of way (ROW). Investigation is required.
HeldWaiting on Quote AcceptanceA quote has been created and is ready for your acceptance.
HeldSchedule ScopingScoping for this order is to be scheduled.
HeldSchedule InstallThe required installation date needs to be scheduled.
HeldIntent to CancelChorus has advised the intent to cancel the order and provided a reason for the cancellation.
HeldProvider to AdviseProvide information to Chorus so the order can progress.
HeldPending Disconnect AcceptanceReview the order and either accept/reject our disconnection notification.
Service GivenService GivenInstallation work is complete. The end user can now use the service at their location.
CompletedBillingBilling is complete.
ClosedCancelledThe order has been cancelled and closed.
ClosedCompletedThe order has been completed and closed.
Site visit order types

With site visit

The following reference table summarises which attributes/arrays are required for order types with a site visit.

With site visitConnect PrimaryConnect Additional ONTConnect SecondaryConnect and ReplaceModify AttributeChange OfferTransfer PrimaryTransfer SecondaryMove PrimaryMove Additional; ONTDisconnect PrimaryDisconnect Secondary
connectRFSDateTimeNoNoNoNoNoNoNoNoNoNoNoNA
disconnectRFSDateTimeNoNoNoNoNoNoNoNoNoNoNoNA
productOfferDetailsYesYesYesYesC1C2YesYesYesYesNoNA
cseProductOfferDetailsOptionalOptionalYesOptionalYesOptionalOptionalOptionalOptionalOptionalYesNA
contactDetailsC5C5C5C5C5C5C5C5C5C5C5NA
locationDetails.siteAccessInformationOptionalNAOptionalOptionalOptionalOptionalOptionalOptionalOptionalNAOptionalNA
locationDetails.LocationOfEquipmentC3C3C3C3C3C3C3C3C3C3C3NA
locationDetails.retainCopperOptionalOptionalOptionalOptionalOptionalOptionalOptionalOptionalOptionalNAOptionalNA
customerDetails.endCustomerYesYesYesYesYesYesYesYesYesYesYesNA
customerDetails.providerReferenceYesYesYesYesYesYesYesYesYesYesYesNA
customerDetails.notificationPreferenceYesYesYesYesYesYesYesYesYesYesYesNA
customerDetails.notificationEmailC4C4C4C4C4C4C4C4C4C4C4NA
billingDetails.billingAccountYesYesYesYesYesYesYesYesYesYesYesNA

Key:

  • C1 - productOfferDetails is required if an RSP wants to modify the characteristics. This is optional if the intention is to order CSE product only.
  • C2 - productOfferDetails is optional for change offer, if the old product offer and new product offer have same characteristics, and the RSP wants to use the same character value.
  • C3 - locationDetails.LocationOfEquipment is required when the market segment is Business or Education.
  • C4 - notificationEmail is required if notificationPreference is Notify.
  • C5 – contactDetails – the site contact is always required when there is a site visit, and orderContact and itContact are always required when there is a site visit and the market segment is Business or Education.

Without site visit

The following reference table summarises which attributes/arrays are required for order types without a site visit.

Without site visitConnect PrimaryConnect Additional ONTConnect SecondaryConnect and ReplaceModify AttributeChange OfferTransfer PrimaryTransfer SecondaryMove PrimaryMove Additional; ONTDisconnect PrimaryDisconnect Secondary
connectRFSDateTimeYesNAYesYesYesYesYesYesYesNANoNo
disconnectRFSDateTimeNoNANoNoNoNoNoNoYesNAYesYes
productOfferDetailsYesNAYesYesYesC2YesYesYesNANoNo
cseProductOfferDetailsNoNANoOptionalNoNoNoNoNoNANoNo
contactDetailsOptionalNAOptionalOptionalOptionalOptionalOptionalOptionalOptionalNAOptionalOptional
locationDetails.siteAccessInformationOptionalNAOptionalOptionalOptionalOptionalOptionalOptionalOptionalNAOptionalOptional
locationDetails.LocationOfEquipmentC3NAC3C3C3C3C3C3C3NAC3C3
locationDetails.retainCopperOptionalNAOptionalOptionalOptionalOptionalOptionalOptionalOptionalNAOptionalOptional
customerDetails.endCustomerYesNAYesYesYesYesYesYesYesNAYesYes
customerDetails.providerReferenceYesNAYesYesYesYesYesYesYesNAYesYes
customerDetails.notificationPreferenceYesNAYesYesYesYesYesYesYesNAYesYes
customerDetails.notificationEmailC4NAC4C4C4C4C4C4C4NAC4C4
billingDetails.billingAccountYesNAYesYesYesYesYesYesYesNAYesYes

Key:

  • C2 - productOfferDetails is optional for change offer, if the old product offer and new product offer have same characteristics, and the RSP wants to use the same character value.
  • C3 - locationDetails.LocationOfEquipment is required when the market segment is Business or Education.
  • C4 - notificationEmail is required if notificationPreference is Notify.

Refer to the API Specification for more information on all available resources, attributes, parameters, field types, length, and other restrictions.


Reviews